home *** CD-ROM | disk | FTP | other *** search
- Path: news.netxpress.com!root
- From: ghporter@NetXpress.com (Glenn H. Porter)
- Newsgroups: comp.lang.c++
- Subject: Re: works in Borland but not in Microsuck Visual C++
- Date: Thu, 21 Mar 1996 14:18:32 GMT
- Organization: Digital Alpha Server NetXpress.com
- Message-ID: <4irokl$j1b@ferrari.NetXpress.com>
- References: <4ia6h8$jes@news.vanderbilt.edu>
- NNTP-Posting-Host: ppp-1-18.netxpress.com
- X-Newsreader: Forte Free Agent 1.0.82
-
- haseltbt@ctrvax.vanderbilt.edu (Bennett Haselton) wrote:
-
- Bennett,
-
- I have to agree with others who have responded to say that you didn't
- initialize your pointer. Now, why will Borland C++ let you do this
- while VC++ won't? Because Borland likes to hold hands and keep the
- programmer from tripping on his own, er, whatever. The response that
- pointed out that MS compilers will let you write a nice tight circle
- around code without letting you know about it are right. Borland lets
- you know about this while MS doesn't care. Sorta like cutting class
- in you freshman year...it's your money (code).
-
- My big complaint with VC++ is that I like Visual Basic and its
- development environment, allowing you to write for Windows without
- having to spend the week in books to find out how to change the width
- of a window border or such nonsense. I bought VC++ thinking that I
- could dump my use of basic once and for all. NOT! I also don't like
- the automatic use of background compilation. When I compile, I want
- it done when I push the mouse button, not a long time later. I want
- to see if I did what I think I did with my code, and I want it now! I
- do like some functionality that VC++ has, but the comfort adjustment
- curve for this product is awfully steep.
-
- Regards,
- Glenn
-
-
-